When Dynamics does not use the SmartDataField cache
Progress Dynamics does not use the SmartDataField cache for dynamic lookups or combos in certain situations, even if the cache is enabled for use.
Cache not used for dynamic lookups
Dynamics does not use the cache for dynamic lookups in the following circumstances:
- When the dynamic lookup has a parent filter query where the values of the parent filter fields do not match the values of the data already in the cache.
- When the Lookup
button is chosen or the F4 key is pressed to launch the lookup browser, the data to be displayed in the browser is still retrieved directly from the server as in previous releases. - When a value is entered in the lookup field and the user leaves the field, either by tabbing off the field or using any other mouse or keyboard event that causes the lookup field to lose focus.
- When the base query string in the lookup does not exactly match the base query string of the data already in the cache.
Cache not used for dynamic combos
Dynamics does not use the cache for dynamic combos in the following circumstances: